Internet Surfer: Getting Started/Internet Surfer - Getting Started (Wayzata Technology)(7231)(1995).bin/pc/textfile/mac_faqs/x_faq/part1

Internet Message Format | 1995-01-01 | 64.0 KB

Xref: bloom-picayune.mit.edu comp.windows.x:61854 news.answers:4486
Newsgroups: comp.windows.x,news.answers
Path: bloom-picayune.mit.edu!enterpoop.mit.edu!eff!sol.ctr.columbia.edu!caen!uunet!visual!dbl
From: [e-mail] (David B. Lewis)
Subject: comp.windows.x Frequently Asked Questions (FAQ) 1/4
Message-ID: <[e-mail]>
Followup-To: poster
Summary: useful information about the X Window System
Reply-To: [e-mail] (X FAQ maintenance address)
Organization: Visual
Date: Tue, 8 Dec 92 14:50:28 GMT
Approved: [e-mail]
Expires: Sun, 03 Jan 1993 00:00:00 GMT
Lines: 1224

Archive-name: x-faq/part1
Last-modified: 1992/12/07

This article and several following contain the answers to some Frequently Asked
Questions (FAQ) often seen in comp.windows.x. It is posted to help reduce
volume in this newsgroup and to provide hard-to-find information of general
interest.

        Please redistribute this article!

This article includes answers to the following questions, which are loosely
grouped into categories. Questions marked with a + indicate questions new to
this issue; those with significant changes of content since the last issue are
marked by !:

  0)  TOPIC: BASIC INFORMATION SOURCES AND DEFINITIONS
  1)  What books and articles on X are good for beginners?
  2)! What courses on X and various X toolkits are available?
  3)! What conferences on X are coming up?
  4)  What X-related public mailing lists are available?
  5)  How can I meet other X developers?
  6)  What related FAQs are available?
  7)  How do I ask a net-question so as to maximize helpful responses?
  8)! What publications discussing X are available?
  9)  What are these common abbreviations/acronyms?
 10)  What is the ICCCM? (How do I write X-friendly applications?)
 11)  What is the X Consortium, and how do I join?
 12)  Just what are OPEN LOOK and Motif?
 13)  Just what is OpenWindows?
 14)  Just what is DECWindows?
 15)  What is PEX?
 16)  What is "low-bandwidth X" (LBX)? XRemote? PPP? SLIP? CSLIP?
 17)  TOPIC: USING X IN DAY-TO-DAY LIFE
 18)! What are all these different window managers?
 19)  Why does my X session exit when I kill my window manager (sic)?
 20)  Can I save the state of my X session, like toolplaces does?
 21)  How do I use another window manager with DEC's session manager?
 22)  How do I change the keyboard auto-repeat rate?
 23)  How do I remap the keys on my keyboard to produce a string?
 24)! How do I make a screendump or print my application?
 25)! How do I make a color PostScript screendump of the X display?
 26)  How do I make a screendump including the X cursor?
 27)! How do I convert/view Mac/TIFF/GIF/Sun/PICT/img/FAX images in X?
 28)  How can I change the titlebar of my xterm window?
 29)  Where can I find the xterm control sequences?
 30)  Why does the R3 xterm, et al, fail against the R4 server?
 31)  How can I use characters above ASCII 127 in xterm ?
 32)  Why are my xterm menus so small?
 33)  How can I print the current selection?
 34)  How does Xt use environment variables in loading resources?
 35)  How to I have the R4 xdm put a picture behind the log-in window?
 36)  Why isn't my PATH set when xdm runs my .xsession file?
 37)  How do I keep my $DISPLAY when I rlogin to another machine?
 38)  How can I design my own font?
 39)  Why does adding a font to the server not work (sic)?
 40)  How do I convert a ".snf" font back to ".bdf" font?
 41)  What is a general method of getting a font in usable format?
 42)  How do I use DECwindows fonts on my non-DECwindows server?
 43)  How do I add ".bdf" fonts to my DECwindows server?
 44)  How can I set the backgroundPixmap resource in a defaults file?
 45)  Why can't I override translations? Only the first item works.
 46)  How can I have xclock or oclock show different timezones?
 47)  I have xmh, but it doesn't work. Where can I get MH?
 48)  Why am I suddenly unable to connect to my Sun X server?
 49)  Why don't the R5 PEX demos work on my mono screen?
 50)  How do I get my Sun Type-[45] keyboard fully supported by Xsun?
 51)  How do I report bugs in X?
 52)  Why do I get "Warning: Widget class version mismatch"?
 53)  Where can I find a dictionary server for xwebster?
 54)  TOPIC: OBTAINING X AND RELATED SOFTWARE AND HARDWARE
 55)  Is X public-domain software?
 56)  How compatible are X11R3, R4, and R5? What changes are there?
 57)  Where can I get X11R5 (source and/or binaries)?
 58)! Where can I get patches to X11R5?
 59)  What is the xstuff mail-archive?
 60)  Where can I get X11R4 (source and binaries)?
 61)! Where can I get OSF/Motif?
 62)! Does Motif work with X11R4? X11R5?
 63)  Where can I get toolkits implementing OPEN LOOK?
 64)  Where can I get other X sources? (including R5 modifications)
 65)! Where can I get interesting widgets?
 66)  What is the current state of the world in X terminals?
 67)  Where can I get an X server with a touchscreen or lightpen?
 68)  Where can I get an X server on a PC (DOS or Unix)?
 69)  Where can I get an X server on a Macintosh running MacOS?
 70)  Where can I get X for the Amiga?
 71)  Where can I get a fast X server for a workstation?
 72)  Where can I get a server for my high-end Sun graphics board?
 73)  Where can I get an "X terminal" server for my low-end Sun 3/50?
 74)  What terminal emulators other than xterm are available?
 75)! Where can I get an X-based editor or word-processor?
 76)  Where can I get an X-based mailer?
 77)! Where can I get an X-based paint/draw program?
 78)  Where can I get an X-based plotting program?
 79)  Where can I get an X-based spreadsheet?
 80)  Where can I get X-based project-management software?
 81)  Where can I get an X-based PostScript previewer?
 82)  Where can I get an X-based GKS package?
 83)  Where can I get an X-based PEX package?
 84)! Where can I get an X-based TeX or DVI previewer?
 85)  Where can I get an X-based troff previewer?
 86)! Where can I get a WYSIWYG interface builder?
 87)  Where can I find X tools callable from shell scripts?
 88)  Where can I get an X-based debugger?
 89)  How can I "tee" an X program identically to several displays?
 90)  TOPIC: BUILDING THE X DISTRIBUTION [topic needs updating to R5]
 91)  What's a good source of information on configuring the X build?
 92)  Why doesn't my Sun with a cg6 work with R5?
 93)  Why doesn't my Sun with SunOS 4.1 know about _dlsym, etc.?
 94)  What is this strange problem building X clients on SunOS 4.1.2?
 95)  Why can't gcc compile X11R4 on my SPARC?
 96)  What are these I/O errors running X built with gcc?
 97)  What are these problems compiling X11R4 on the older Sun3?
 98)  What are these problems compiling the X server on SunOS 4.1.1?
 99)  What are these problems using R4 shared libraries on SunOS 4?
100)  Can OLIT programs run with R5 Xt? (_XtQString undefined)
101)  How do I get around the SunOS 4.1 security hole?
102)  TOPIC: BUILDING X PROGRAMS
103)  What is Imake?
104)  Where can I get imake?
105)  I have a program with an Imakefile but no Makefile. What to do?
106)  Why can't I link to the Xlib shape routines?
107)  What are these problems with "_XtInherit not found" on the Sun?
108)  Why can't I compile my R3 Xaw contrib programs under the new X?
109)  TOPIC: PROGRAMMING PROBLEMS AND PUZZLES
110)  Why doesn't my program get the keystrokes I select for (sic)?
111)  How do I figure out what window manager is running?
112)  Is there a skeleton X program available?
113)  Why does XtGetValues not work for me (sic)?
114)  Why don't XtConfigureWidget/XtResizeWidget/XtMoveWidget work?
115)  Why isn't there an XtReparentWidget call like XReparentWindow?
116)  I'm writing a widget and can't use a float as a resource value.
117)  Is this a memory leak in the X11R4 XtDestroyWidget()?!
118)  Are callbacks guaranteed to be called in the order registered?
119)  Why doesn't XtDestroyWidget() actually destroy the widget?
120)  How do I query the user synchronously using Xt?
121)  How do I determine the name of an existing widget?
122)  What widget is appropriate to use as a drawing canvas?
123)  Why do I get a BadDrawable error drawing to XtWindow(widget)?
124)  Why do I get a BadMatch error when calling XGetImage?
125)  How can my application tell if it is being run under X?
126)! How do I make a "busy cursor" while my application is computing?
127)  How do I fork without hanging my parent X program?
128)  Can I make Xt or Xlib calls from a signal handler?
129)  What are these "Xlib sequence lost" errors?
130)  How can my Xt program handle socket, pipe, or file input?
131)  How do I simulate a button press/release event for a widget?
132)  Why doesn't anything appear when I run this simple program?
133)  What is the difference between a Screen and a screen?
134)  Can I use C++ with X11? Motif? XView?
135)! Where can I obtain alternate language bindings to X?
136)  Can XGetWindowAttributes get a window's background pixel/pixmap?
137)  How do I create a transparent window?
138)  Why doesn't GXxor produce mathematically-correct color values?
139)  Why does every color I allocate show up as black?
140)  Why can't my program get a standard colormap?
141)  Why does the pixmap I copy to the screen show up as garbage?
142)  How do I check whether a window ID is valid?
143)  Can I have two applications draw to the same window?
144)  Why can't my program work with tvtwm or swm?
145)  How do I keep a window from being resized by the user?
146)  How do I keep a window in the foreground at all times?
147)  How do I make text and bitmaps blink in X?
148)  How do I render rotated text?
149)  What is the X Registry? (How do I reserve names?)

If you have suggestions or corrections for any of these answers or any
additional information, please send them directly to uunet!craft!faq;
the information will be included in the next revision (or possibly the one
after that; thanks for the many suggestions which haven't been incorporated
yet).

This version of the FAQ is in the process of having R3 information replaced
by R5 information.

This posting is intended to be distributed at approximately the beginning of
each month. New versions are archived on export.lcs.mit.edu and are also
available from [e-mail] (send "help").

The information contained herein has been gathered from a variety of sources.
In many cases attribution has been lost; if you would like to claim
responsibility for a particular item, please let me know.

Conventions used below: telephone numbers tend to be Bell-system unless
otherwise noted; prices on items are not included; email addresses are those
that work from the US.

All trademarks are the property of their respective owners.

----------------------------------------------------------------------
Subject:   0)  TOPIC: BASIC INFORMATION SOURCES AND DEFINITIONS
----------------------------------------------------------------------
Subject:   1)  What books and articles on X are good for beginners?

    Ken Lee of the DEC Western Software Laboratory ([e-mail])
regularly posts to comp.windows.x and ba.windows.x a bibliography containing
cites of all known reference books and how-to manuals and also cites of
selected technical articles on X and X programming; it is ftp-able as
    export.lcs.mit.edu:/contrib/Xbibliography and
    gatekeeper.dec.com:/pub/X11/contrib/Xbibliography

Here is an unordered set of the reference books and tutorials most useful for
beginners; most appear on that list [comments are gathered from a variety of
places and are unattributable]:

Asente, Paul J., and Swick, Ralph R., "X Window System Toolkit, The Complete
Programmer's Guide and Specification", Digital Press, 1990.  The bible on Xt. A
treasury of information, excellent and invaluable.  Distributed by Digital
Press, ISBN 1-55558-051-3, order number EY-E757E-DP; and by Prentice-Hall,
ISBN 0-13-972191-6. Also available through DEC Direct at 1-800-DIGITAL.
[The examples are on export.lcs.mit.edu in contrib/ and on gatekeeper.dec.com
(16.1.0.2) in pub/X11/contrib as asente-swick.examples.tar.Z.  They were also
posted to comp.sources.x as xt-examples/part0[1-5].]

Jones, Oliver, Introduction to the X Window System, Prentice-Hall, 1988, 1989.
ISBN 0-13-499997-5. An excellent introduction to programming with Xlib.
Written with the programmer in mind, this book includes many practical tips
that are not found anywhere else. This book is not as broad as the O'Reilly
Xlib tutorial, but Jones is an experienced X programmer and this shows in the
quality and depth of the material in the book. Originally written for X11R1,
recent printings have included corrections and additions and current material.

Young, Doug. "The X Window System: Applications and Programming with Xt (Motif
Version)," Prentice Hall, 1989 (ISBN 0-13-497074-8). The excellent tutorial
"X Window Systems Programming and Applications with Xt," (ISBN 0-13-972167-3)
updated for Motif. [The examples are available on export; the ones from the
Motif version are in ~ftp/contrib/young.motif.tar.Z.]

Young, Doug and John Pew, "The X Window System: Programming and Applications
with Xt, OPEN LOOK Edition" (ISBN 0-13-982992-X). The tutorial rewritten for
OLIT, with new examples and drag/drop information. [Examples are on export in
youg.olit.tar.Z.]

Heller, Dan. "Motif Programmers Manual". The 6th Volume in the O'Reilly series
covers Motif application programming; it's full of good examples. With Motif
reference pages. (ISBN 0-9937175-70-6.)  [The examples are available on uunet
in comp.sources.x and nutshell archives.]

Scheifler, Robert, and James Gettys, with Jim Flowers and David Rosenthal, "X
Window System: The Complete Reference to Xlib, X Protocol, ICCCM, XLFD, X
Version 11, Release 5, Third Edition," Digital Press, 1992. "The Bible" in its
latest revision", an enhanced version of X documentation by the authors of the
Xlib documentation. This is the most complete published description of the X
programming interface and X protocol. It is the primary reference work and is
not introductory tutorial documentation; additional tutorial works will usually
be needed by most new X programmers.  Digital Press order EY-J802E-DP, ISBN
0-13-971201-1.

Nye, Adrian, "Xlib Programming Manual, Volume 1" and "Xlib Reference Manual,
Volume 2," O'Reilly and Associates, 1988. A superset of the MIT X
documentation; the first volume is a tutorial with broad coverage of Xlib, and
the second contains reference pages for Xlib functions and many useful
reference appendices.  ISBN 0-937175-26-9 (volume 1) and ISBN 0-937175-27-7
(volume 2).  [A version updated for X11R4 is available (4/90).]

Nye, Adrian, and Tim O'Reilly, "X Toolkit Programming Manual, Volume 4,"
O'Reilly and Associates, 1989. The folks at O'Reilly give their comprehensive
treatment to programming with the MIT Intrinsics; R4 versions are now
available, as is a Motif 1.1 version (Volume 4M).

O'Reilly, Tim, ed.,  "X Toolkit Reference Manual, Volume 5," O'Reilly and
Associates, 1989.  A professional reference manual for the MIT X11R3 Xt; some
information on X11R4 is included.

Mansfield, Niall. "The X Window System: A User's Guide," Addison-Wesley, 1989.
A tutorial introduction to using X, now upgraded for R4. ISBN 0-201-51341-2.

Quercia, Valerie and Tim O'Reilly. "X Window System User's Guide," O'Reilly and
Associates, 1989. A tutorial introduction to using X. ISBN 0-937175-36-6.
Also available in R4 and Motif flavors.

(Prentice-Hall ordering is 201-767-5937. O'Reilly ordering is 800-998-9938.)

In addition, check the X11R4 and X11R5 core distribution in doc/tutorials for
some useful papers and tutorials, particularly the file answers.txt.  "Late
Night's Top Ten X11 Questions" by Dave Lemke ([e-mail]) and Stuart Marks
([e-mail]) answers other common questions and some of these here in more
detail.

New R5 versions of the O'Reilly references (not yet Volume 6) are now available
[8/92].  A single volume, "Programmer's Supplement for R5" by David Flanagan,
provides an overview of new R5 features; it includes man pages for Xlib, Xt,
and Xmu. [ISBN  0-937175-86-2]

----------------------------------------------------------------------
Subject:   2)! What courses on X and various X toolkits are available?

    Advanced Computing Environments periodically offers at least a two-day
Introduction course. Contact Susie Karlson at 415-941-3399 for information.

    AT&T offers training in Xlib and in the Xol set. Contact AT&T Corporate
Education & Training for more info; 1-800-TRAINER in the USA.

    Communica Software Consultants offers three-day hands-on courses in X
designed for the X Window system developer and programmer. Contact Chris
Clarkson, telephone [phone], e-mail [e-mail]. [5/91]

    Cora Computer Technologies (516-485-7343) offers several courses.

    GHCT offers a one week lecture/lab course for programmmers designed by
Douglas Young based on his book "The X Window System: Programming and Applica-
tions with Xt, OSF/Motif Edition". Information: Brian Stell (415-966-8805 or
ghct![e-mail]).

    GHG offers a range of courses on X and Motif. Information: 713-488-8806
or [e-mail].

    Hands On Learning has live training and self-paced video workshops on
topics such as using and/or programming X, Xlib, Xm, Xt, and widget-writing.
Information: 617-272-0088, 800-248-9133.

    Hewlett-Packard (1-800-HPCLASS; or contact your local HP center) offers
a 2-day "Introduction to X", a 5-day Xlib course, a 1-day Xt and Motif 1.1
seminar, and a 5-day Motif lab course.

    Integrated Computer Solutions, Inc., offers several multi-day, hands-on
courses on X, Xt, and the Xaw and Motif widget sets, in particular. Information
is available at 617-621-0060 and [e-mail].

    Intelligent Visual Computing teaches several lab courses on-site for
Motif and XView. IVC is at 1-800-776-2810 or [phone] or at [e-mail].

    Iris Computing Laboratories offers five-day Xlib and Xt courses.
Info: [phone] or [e-mail].

    IXI Limited ([phone]) offers regular X training courses for
both programmers and non-technical managers. See also: Unipalm, below.

    Learning Tree International offers a four-day course in X Window System
applications development, including Xlib and some information on Motif.  For
more info call 800-824-9155 (213-417-3484); 613-748-7741 in Canada. Courses are
offered in major North American cities; also in London, Stockholm, Tokyo, and
elsewhere.

    Lurnix offers 4-day "type-along courses" on Xt; the course is being
ported from Xaw to Xm. Information is available at 800-433-9337 (in CA: -9338).

    Mitch Trachtenberg and Associates offers regular 5-day lab courses on
programming with OSF/Motif, usually in but not limited to Cambridge, MA.
Info: [phone], [e-mail].

    Non Standard Logics ([phone]; [e-mail]) offers
courses on programming with Xlib, Motif, and creating Motif widgets.

    OSF Educational Services (617-621-8778) offers one-day seminars and
one-week Motif lab courses.

    John A. Pew offers a 5-day course on OLIT, possibly based on his book
on that subject; 408-224-5739.

    SCO ([phone], [e-mail]) offers training for its Open
Desktop (Motif) environment in the UK and Europe.

    Software Pundits (617-270-0639) offers a range of courses.

    Technology Exchange (617-944-3700) offers a 4-day Xlib/Xt/Motif course.

    TeleSoft is now offering a 1-day plus 3-day seminar on X and Motif.
Information: Bruce Sherman (619-457-2700, [e-mail]).

    Unipalm XTech offers OSF's 5-day Motif course and a 1-day overview on
X.  Information: Unipalm Training at [phone], [e-mail].

    Various other vendors are also beginning to offer X training, usually
specific to a proprietary toolkit or to Xt and a proprietary widget set: DEC
is offering Xlib courses; Sun offers an XView course.

    Various universities are offering short X courses or overviews: UCLA,
Dartmouth, University of Lowell, University of Canberra (within Australia:
062-522422) ...
    UC Berkeley Extension will have a one week X/Motif class for
programmers in San Francisco starting on July 29.  The class will have a
hands-on lab. For more information contact UCBX at 415 323 8141.

    Among the best places to find courses are at the various Unix
conferences -- Uniforum, Usenix, Unix Expo, Xhibition, the MIT X Technical
Conference, the ACM tutorial weeks, &c.

    In addition, the X Consortium posts approximately quarterly a list of
unendorsed speakers and consultants who can provide talks on a variety of X
topics.

----------------------------------------------------------------------
Subject:   3)! What conferences on X are coming up?

    The MIT X Technical Conference is typically held in January in Boston.
The 7th will be held January 18-20, 1993 at the Sheraton Boston Hotel and
Towers.  Registration information is available from
[e-mail].

    The XWorld Conference and Exhibition includes tutorials, panels,
presentations and vendor exhibits. The '93 show is April 19-23 in New York
City.  Information: SIGS Publication Group at 212-274-0640.

    The Xhibition 93 X trade show and conference, with tutorials, panels,
presentations, and vendor exhibits, will be held at the San Jose Convention
Center June 7-11, 1993.  Information: [phone], [e-mail].

    The European X User Group holds an annual conference which typically
includes includes paper presentations and a vendor exhibit. Information:
[e-mail] (?) or [e-mail], [phone],
fax [phone].

    The Motif show is held in Washington to coincide with the FedUnix and
the Federal Open Systems Conference (usually December). Information:
[e-mail] or [e-mail], 301-229-1062, fax [phone].

    Other trade shows -- UnixExpo, Uniforum, Siggraph -- show an increasing
presence of X, including tutorials and exhibits.

----------------------------------------------------------------------
Subject:   4)  What X-related public mailing lists are available?

    The xpert mailing list is the general, public mailing list on X
maintained by the X Consortium. The mailings are gatewayed, so xpert is almost
identical to the comp.windows.x Usenet newsgroup.

    ***    If you get comp.windows.x, you don't need to     ***
    ***    be added to the xpert mailing list.         ***

    Otherwise, you can join the list to receive X information
electronically. It is best to find a local distribution; perhaps someone within
your company is already receiving the mailing. As a last resort, send mail to
[e-mail] with a valid return electronic address.

    The xannounce mailing list carries major X announcements, such as new
releases (including public patches from MIT), public reviews, adoption of
standards by the MIT X Consortium, and conference announcements.  It does NOT
carry advertisements, source code, patches, or questions.  If you already
receive the Usenet news group comp.windows.x.announce or the xpert mailing list,
you don't need to be added to the xannounce mailing list.  Otherwise, to
subscribe, send a request to [e-mail]. Note: Only
redistribution addresses will be accepted for this list -- i.e. no personal
addresses. If you wish to receive xannounce yourself, please contact your mail
administrator to set up a local redistribution list and to put you on it.
    comp.windows.x.apps is not gatewayed to a mailing list.

    In addition, the X Consortium sponsors these public lists:
        bug-clx         CLX bug reports and discussions
        x-ada           X and ada
        x11-3d          people interested in X and 3d graphics
        ximage          people interested in image processing and X
        xvideo          discussion of video extensions for X
    To subscribe to one of these lists, assuming no-one in your
organization already receives it, send mail to <list>[e-mail]
with the Subject line including the name of the LIST in caps and the request
"addition request".  In the body of the message be sure to give an address for
your local distribution which is accessible from MIT (eddie.mit.edu).

    A mailing list for topics related to OPEN LOOK is sponsored by Greg
Pasquariello of Unify corporation; send to [e-mail] (or
[e-mail]) for information.
    A mailing list for bugs in the publicly-available version of XView
source, in particular, is sponsored by Sun; send for information to
[e-mail].
    A mailing list for topics related to Motif is sponsored by Kee Hinckley
of Alfalfa Software, Inc.; send to [e-mail] for information.
(This group is gatewayed to comp.windows.x.motif.)
    A mailing list for topics related to the XPM pixmap-format is sponsored
by Arnaud Le Hors of Group Bull; send to [e-mail] for
information. [1/91]
    A mailing list discussing InterViews can be subscribed to by sending to
[e-mail].
    A mailing list ([e-mail]) for topics related to the port
of X11 to the Amiga can be subscribed by sending to [e-mail] a
message containing
        Subject: Adding myself to AMIGA-X11
        SUBS AMIGA-X11 Your Real Name
    A mailing list discussing ParcPlace's (formerly Solbourne's) OI (Object
Interface) toolkit can be subscribed to at [e-mail].
    A mailing list discussing multi-threaded Xlib can be subscribed to at
[e-mail].

----------------------------------------------------------------------
Subject:   5)  How can I meet other X developers?

    O'Reilly and Associates sponsors a mailing list for the use of X user
group organizers; subscribe by sending to [e-mail] the message
"subscribe xgroups [e-mail]".

    Local area X user's groups are listed in Issue 4 of O'Reilly's X
Resource journal; a list may also be available from [e-mail].

    The French X User Group is called AFUX and is based in Sophia Antipolis
by CERICS. Information can be obtained from Miss Vasseur or Miss Forest; BP
148; 157, rue Albert Einstein; 06561 Valbonne Cedex; Phone: [phone] /
45 01; Fax: [phone].  [10/90]

    The European X User Group was formed in 1989 to represent X users in
Europe.  It holds technical conferences at regular intervals. The EXUG also
publishes a regular newsletter which is distributed free of charge to members.
The EXUG also runs a email mailing list for members which is frequently used to
address issues of European interest in X. The EXUG can be contacted at
[e-mail], [phone], fax [phone].

    GXUGiV is the German X User's Group in Vorbereitung ("in preparation")
being formed for X programmers and users; it is associated with the EXUG. All
interested should contact Olaf Heimburger ([phone]; and at
mcvax!unido!tub!olaf).

----------------------------------------------------------------------
Subject:   6)  What related FAQs are available?

    Liam R. E. Quin ([e-mail]) posts a FAQ on Open Look to
comp.windows.open-look.
    Jan Newmarch ([e-mail]) posts a FAQ on Motif to
comp.windows.x.motif.
    Peter Ware ([e-mail]) posts a FAQ for
comp.windows.x.intrinsics; it is on export in contrib/FAQ-Xt.
    Art Mulder ([e-mail]) posts to comp.windows.x a FAQ on
maximizing the performance of X.
    Steve Kotsopoulos ([e-mail]) posts to comp.windows.x a FAQ
about using X on Intel-based Unix systems.
    The FAQ in alt.binaries.pictures contains information on viewing images
with X and on massaging image formats.
    The FAQ in comp.mail.mh (gatewayed to [e-mail]) includes a
section on xmh.
    The FAQ in comp.lang.lisp contains information on several interface
tools and toolkits.
    There exists a PEX/PHiGS FAQ.

----------------------------------------------------------------------
Subject:   7)  How do I ask a net-question so as to maximize helpful responses?

    When asking for help on the net or X mailing lists, be sure to include
all information about your setup and what you are doing.  The more specific you
are, the more likely someone will spot an error in what you are doing.  Without
all the details, people who want to help you often have to guess -- if they are
able to respond at all.

    Always mention what version of X you are using and where you got it
from. If your server came from a different source as the rest of your X system,
give details of that, too.  Give the machine type, operating system, and O/S
version for both the client and server machine.  It may also be appropriate to
mention the window manager, compiler, and display hardware type you are using.

    Then tell exactly what you are doing, exactly what happens, and what
you expected/wanted to happen.  If it is a command that fails, include the
exact transcript of your session in the message.  If a program you wrote
doesn't work the way you expect, include as little of the source necessary
(just a small test case, please!) for readers to reproduce the problem.

----------------------------------------------------------------------
Subject:   8)! What publications discussing X are available?

    The trade magazines (Unix World, Unix Review, Computer Language, etc.)
are publishing more articles on X.  Two X-specific publications include:

    - O'Reilly and Associates publishes "The X Resource: A Practical
Journal of the X Window System" (103 Morris St. #A, Sebastapol, CA 95472).
Editorial information: Adrian Nye, [e-mail].

    - The X Journal is started bi-monthly publication September 1991 on a
variety of X topics. Subscription information: The X Journal, Subscriber
Services, Dept XXX, P.O. Box 3000, Denville, NJ 07834, USA. Editorial
information: [e-mail].

----------------------------------------------------------------------
Subject:   9)  What are these common abbreviations/acronyms?

    Xt: The X Toolkit Intrinsics is a library layered on Xlib which
provides the functionality from which the widget sets are built. An "Xt-based"
program is an application which uses one of those widget sets and which uses
Intrinsics mechanisms to manipulate the widgets.
    Xmu: The Xmu library is a collection of Miscellaneous Utility functions
useful in building various applications and widgets.
    Xaw: The Athena Widget Set is the MIT-implemented sample widget set
distributed with X11 source.
    Xm: The OSF/Motif widget set from the Open Software Foundation; binary
kits are available from many hardware vendors.
    Xhp (Xw): The Hewlett-Packard Widget Set was originally based on R2++,
but several sets of patches exist which bring it up to R3, as it is distributed
on the X11R4 tapes. Supplemental patches are available to use it with R4/R5.
    CLX: The Common Lisp X Interface is a Common Lisp equivalent to Xlib.
    XDMCP: The X Display Manager Protocol provides a uniform mechanism for
a display such as an X terminal to request login service from a remote host.
    XLFD: The X Logical Font Description Conventions describes a standard
logical font description and conventions to be used by clients so that they
can query and access those resources.
    RTFM: Common expert-speak meaning "please locate and consult the
relevant documentation -- Read the Forgotten Manual".
    UTSL: A common expression meaning "take advantage of the fact that you
aren't limited by a binary license -- Use The Source, Luke".
    API: Application-Programmer Interface. The function calls, etc., in
a programming library.
    BDF: Bitmap Distribution Format; a human-readable format for uncompiled X fonts.
    GUI: graphical user interface.
    UIL: the User Interface Language, part of OSF/Motif which lets
programmers specify a widget hierarchy in a simple "outline" form
    WCL: the Widget Creation Language, a package which extends the
understanding of the Xt resource format such that a widget hierarchy and
actions on the widgets can be specified through the resources file
    GIL: the file format put out by Sun's OpenWindows Developers Guide 3.0
    UIMS: User Interface Management System

----------------------------------------------------------------------
Subject:  10)  What is the ICCCM? (How do I write X-friendly applications?)

    The Inter-Client Communication Conventions Manual is one of the
official X Consortium standards documents that define the X environment. It
describes the conventions that clients must observe to coexist peacefully with
other clients sharing the same server.  If you are writing X clients, you need
to read and understand the ICCCM,  in particular the sections discussing the
selection mechanism and the interaction between your client and the window
manager.  Get it either:
    - as part of the R4 distribution from MIT
    - in the later editions of the Scheifler/Gettys "X Window System" book
    - as an appendix in the new version of O'Reilly's Volume 0, "X Protocol
Reference Manual." A version in old copies of their Volume 1 is obsolete.
    The version in the Digital Press book is much more readable, thanks to
the efforts of Digital Press's editors to improve the English and the
presentation.

[from David Rosenthal, 10/90]

    - the ICCCM was updated for R5; updates are published in O'Reilly's
"Programmer's Supplement for Release 5". The complete document is on the R5
tapes.

    Alternate definition: the ICCCM is generally the M in "RTFM" and is
the most-important of the least-read X documents.

----------------------------------------------------------------------
Subject:  11)  What is the X Consortium, and how do I join?

    The MIT X Consortium was formed in January of 1988 to further the
development of the X Window System and has as its major goal the promotion of
cooperation within the computer industry in the creation of standard software
interfaces at all layers in the X Window System environment.
    MIT's role is to provide the vendor-neutral architectural and
administrative leadership required to make this work. Membership in the
Consortium open to any organization.  There are two categories of membership,
Member (for large organizations) and Affiliate (for smaller organizations).
    Most of the Consortium's activities take place via electronic mail,
with meetings when required.  As designs and specifications take shape,
interest groups are formed from experts in the participating organizations.
Typically a small multi-organization architecture team leads the design, with
others acting as close observers and reviewers.  Once a complete specification
is produced, it may be submitted for formal technical review by the Consortium
as a proposed standard.  The standards process typically includes public
review (outside the Consortium) and a demonstration of proof of concept.
    Your involvement in the public review process or as a Member or
Affiliate of the Consortium is welcomed.
    Write to: Bob Scheifler, MIT X Consortium, Laboratory for Computer
Science, 545 Technology Square, Cambridge, MA 02139.

[For complete information see the XCONSORTIUM man page from the X11R4
distribution, from which this information is adapted.] [2/90]

----------------------------------------------------------------------
Subject:  12)  Just what are OPEN LOOK and Motif?

    OPEN LOOK and Motif are two graphical user interfaces (GUIs). OPEN LOOK
was developed by Sun with help from AT&T and many industry reviewers; Motif was
developed by the Open Software Foundation (OSF) with input from many OSF
members.

    OPEN LOOK is primarily a user-interface specification and style-guide;
there are several toolkits which can be used to produce OPEN LOOK applications.
Motif includes an API specification; the only sanctioned Motif toolkit is the
one from OSF. However, there are other toolkits which can be used to produce
programs which look and behave like OSF/Motif; one of these, ParcPlace's
(formerly Solbourne's) OI, is a "virtual toolkit" which provides objects in the
style of OPEN LOOK and Motif, at the user's choice.

    OPEN LOOK GUI is also the name of a product from AT&T, comprising
their OPEN LOOK Intrinsics Toolkit and a variety of applications.

[Thanks to Ian Darwin, [e-mail], 5/91]

----------------------------------------------------------------------
Subject:  13)  Just what is OpenWindows?

    Open Windows (3.0) is a Sun product that encompasses: a window system
that combines a NeWS and X11-compliant server (X/NeWS); a user-interface
specification (OPEN LOOK) and a series of toolkits that implement it (including
the SunView-like XView and the Xt-based OLIT); Xlib and Xt implementations; and
a number of utilities (olwm window manager, filemgr, shelltool, etc.).

[thanks to Frank Greco ([e-mail]), 8/90; 4/92]

----------------------------------------------------------------------
Subject:  14)  Just what is DECWindows?

    DECWindows is a DEC product that encompasses: an X11 server; the XUI
toolkit, including the Dwt widget set and UIL; Xlib and Xt implementations; a
session manager; and a number of utilities (dxwm window manager, dxcalendar,
dxpsview, etc.).

(At some point Motif flavors of the toolkit and applications will be shipped.)
[8/90]

----------------------------------------------------------------------
Subject:  15)  What is PEX?

    PEX is the "PHiGS Extension to X".
    PHiGS stands for "Programmer's Hierarchical Interactive Graphics
System" and is essentially a library of functions that simplifies the creation
and manipulation of 3D graphics. Many platforms are capable of performing in
hardware the computations involved in rendering 3D objects; the extension
allows the client (PHiGS in this case) to take advantage of the specialized
hardware for 3D graphics.
    Sun Microsystems is currently contracted to develop a freely
redistributable (copyright similar to the current X copyright) sample
implementation.  Source and documentation are available in the R5 release.
Several vendors are currently selling independently-developed PEX servers for
their workstations and X terminals.

[last modified 10/91]

----------------------------------------------------------------------
Subject:  16)  What is "low-bandwidth X" (LBX)? XRemote? PPP? SLIP? CSLIP?

There are several options for using X over serial lines:

SLIP - Serial Line IP; this is both a mechanism and a protocol for sending IP
packets over point-to-point serial links. It has been around for several years,
and implementations are available for many of the major TCP/IP implementations.
Most X Terminal vendors supply this as a checkoff item, although nobody really
ever uses it since it is horribly slow.  The TCP/IP headers add 40 bytes per
packet and the TCP/IP encoding of the X protocol is rather verbose (rightfully
so; it is optimized for packing and unpacking over high-speed links).

CSLIP - Compressed header SLIP; this is a variant of SLIP that compresses the 40
bytes of TCP/IP headers down to about 5 or 6 bytes.  It still doesn't do
anything about reencoding the X protocol.  Modems that do compression can help,
but they increase packet latency (it takes time to dribble the uncompressed data
through typical serial interfaces, plus the compression assembly time).

PPP - Point-to-Point Protocol; this is an emerging standard for point-to-point
links over serial lines that has a more complete set of option negotiation than
SLIP.  A growing number of people see the combination of PPP for the serial line
management and CSLIP for the header compression as becoming common for running
normal TCP/IP protocols over serial lines.  Running raw X over the wire still
needs compression somewhere to make it usable.

XRemote - this is the name of both a protocol and set of products originally
developed by NCD for squeezing the X protocol over serial lines.  In addition to
using a low level transport mechanism similar to PPP/CSLIP, XRemote removes
redundancies in the X protocol by sending deltas against previous packets and
using LZW to compress the entire data stream.  This work is done by either a
pseudo-X server or "proxy" running on the host or in a terminal server.  There
are several advantages to doing compression outside the modem:
   (1)    You don't *have* to have compressing modems in there if you wouldn't
    otherwise be using them (e.g. if you were going to be directly
    connected), and
   (2)    It reduces the I/O overhead by cutting down on the number of bytes that
    have to cross the serial interface, and
   (3)    In addition to the effects of #2, it reduces the latency in delivering
    packets by not requiring the modem to buffer up the data waiting for
    blocks to compress.

LBX - Low Bandwidth X; this is an X Consortium project that is working on a
standard for this area.  It is being chaired by NCD and Xerox and is using NCD's
XRemote protocol as a stepping stone in developing the new protocol.  LBX will
go beyond XRemote by adding proxy caching of commonly-used information (e.g.
connection setup data, large window properties, font metrics, keymaps, etc.) and
a more efficient encoding of the X protocol. The hope is to have a Standard
ready for public review in the first half of next year and a sample
implementation available in R6.

Additional technical information about how XRemote works and a few notes on how
LBX might be different are available via anonymous ftp from export.lcs.mit.edu
in contrib/ in the following files:
        XRemote-slides.ps               slides describing XRemote
        XRemote-LBX-diffs.ps            more slides describing some of LBX

[information provided by Jim Fulton, [e-mail]; 7/92]

----------------------------------------------------------------------
Subject:  17)  TOPIC: USING X IN DAY-TO-DAY LIFE
----------------------------------------------------------------------
Subject:  18)! What are all these different window managers?

    The window manager in X is just another client -- it is not part of the
X window system, although it enjoys special privileges -- and so there is
no single window manager; instead, there are many which support different ways
for the user to interact with windows and different styles of window layout,
decoration, and keyboard and colormap focus. In approximate chronological order
(generally, the more recent ones are more conformant with the ICCCM):

    wm: this simple title-bar window manager was phased out in R2 or R3
    uwm: the Universal Window Manager is still popular for its speed,
although it is very outdated. Moved to contrib/ on the R4 tape.
    twm (old): Tom's Window Manager was among the first non-MIT window
managers and offered the user a great deal of customization options in a
re-parenting window manager.
    awm: the Ardent Window Manager remains a hotbed for hackers and offers
some features (dynamic menus) not found on more current window managers
    cwm: cwm is part of the Andrew system.
    rtl: Siemen's window manager tiles windows so that they don't overlap
and resizes the window with the focus to its preferred size.
    dxwm: Digital's dxwm is part of the DECwindows offering
    hpwm: HP's window manager offers a 3D look; it is a precursor of mwm
    mwm: the Motif window manager is part of the OSF/Motif toolkit
    tekwm: Tektronix's window manager offering
    olwm (Sun): olwm implements the OPEN LOOK GUI and some of the Style
Guide functionality
    olwm (AT&T): ditto
    gwm: Bull's Generic Window Manager emulates others with a built-in
Lisp interpreter. Version 1.7h (10/91) is on the R5 contrib tape; 1.7m is on
avahi.inria.fr and export.lcs.mit.edu. [8/92]
    m_swm: the Sigma window manager is on the R4 tape
    pswm: Sun's PostScript-based pswm is part of the OpenWindows release
    swm: Solbourne's swm is based on the OI toolkit and offers multiple
GUI support and also a panned virtual window; configuration information comes
from the resources file
    twm (new): MIT's new Tab Window Manager from the R4 tape is a reworked
twm and is the basis for several derivatives, including the one on the R5 tape
    vtwm: vtwm offers some of the virtual-desktop features of swm, with a
single-root window implementation; it is based on the R4 twm and is available
on archive servers. A new version, vtwm-5.0, is based on R5.9 and is available
from export. [3/92]
    tvtwm: Tom's Virtual Tab Window Manager is also based on the R4 twm
and provides a virtual desktop modeled on the virtual-root window of swm. It is
available on archive servers
    olvwm: the vtwm-style virtual-desktop added to Sun's olwm. It is
available on archive servers; version 3.0 [1/92] is on export.
    mvwm: the vtwm-style virtual-desktop added to OSF's mwm. A beta version
is floating around (most recently from [e-mail]) but requires a
source license to OSF/Motif 1.1.3 [3/92].
    NCDwm: the window manager local to NCD terminals offers an mwm look
    XDSwm: the window manager local to Visual Technology's terminals
    ctwm: Claude Lecommandeur's ([e-mail]) modification of the R5
twm offers 32 virtual screens in the fashion of HP vuewm; source is on export.
Version 2.0 also offers the window overview used in vtwm and tvtwm.
    vuewm: HP's MWM-based window manager offers configurable workspaces.
    4Dwm: SGI's enhanced MWM

----------------------------------------------------------------------
Subject:  19)  Why does my X session exit when I kill my window manager (sic)?

    It needn't.  What is probably happening is that you are running your
window manager as the last job in your .xsession or .xinitrc file; your X
session runs only as long as the last job is running, and so killing your
window manager is equivalent to logging out. Instead, run the window manager in
the background, and as the last job instead invoke something safe like:
        exec xterm -name Login -rv -iconic
or any special client of your devising which exits on some user action.
Your X session will continue until you explicitly logout of this window,
whether or not you kill or restart your window manager.

----------------------------------------------------------------------
Subject:  20)  Can I save the state of my X session, like toolplaces does?

    Although no known window manager directly supports such a feature --
which may be equivalent to writing out a .xinitrc or .xsession file naming the
geometry and WM_COMMAND of each application (but olvwm may have something
close) -- there is a contributed application which does much of what you are
looking for, although it is not as complete as the SunView program toolplaces.
Look for the application "xplaces" on an archive-server near you. There are
several versions of this program floating around; look for a recent vintage.
[10/90]

----------------------------------------------------------------------
Subject:  21)  How do I use another window manager with DEC's session manager?

    DEC's session manager will start dxwm up by default. To override this,
add to your .Xdefaults file something like this line, naming the full pathname:
    sm.windowManagerName:   /wherever/usr/bin/X11/your_favorite_wm

----------------------------------------------------------------------
Subject:  22)  How do I change the keyboard auto-repeat rate?

    You can turn auto-repeat on or off by using "xset r on|off". The X
protocol, however, doesn't provide for varying the auto-repeat rate, which is
a capability not supported by all systems.
    Some servers running on systems that support this (the Xsun server from
MIT, for example), however, may provide command-line flags to set the rate at
start-up time. If you have control over server start-up, you can invoke the
server with the chosen settings.

----------------------------------------------------------------------
Subject:  23)  How do I remap the keys on my keyboard to produce a string?

    There is no method of arranging for a particular string to be
produced when you press a particular key. The xmodmap client, which is useful
for moving your CTRL and ESC keys to useful places, just rearranges keys and
does not do "macro expansion."
    Some (few) clients, including xterm and several X-based editors,
accept a translation resource such as:
    xterm*VT100.Translations: #override \
        <Key>F1: string("setenv DISPLAY unix:0")
which permits the shorthand F1 to be pressed to reset the display locally
within an xterm; it takes effect for new xterm clients. To include control
characters in the string, use \nnn, where nnn is the octal encoding of the
control character you want to include.
    Window managers, which could provide this facility, do not yet; nor
has a special "remapper" client been made available.

----------------------------------------------------------------------
Subject:  24)! How do I make a screendump or print my application?

    The xwd client in the X11 distributions can be used to select a window
or the background. It produces an XWD-format file of the image of that window.
The file can be post-processed into something useful or printed with the xpr
client and your local printing mechanism. You can use this command:
        csh% sleep 10; xwd -root > output.xwd &
and then spend 10 seconds or so setting up your screen; the entire current
display will be saved into the file output.xwd. Note that xwd also has an
undocumented (before R5) -id flag for specifying the window id on the
command-line. [There are also unofficial patches on export to xwd for
specifying the delay and the portion of the screen to capture.]

    Two publicly-available programs which allow interactive definition of
arbitrary portions of the display and built-in delays are asnap and xgrabsc.
There are several versions of xgrabsc; version 2.2, available on export [8/92]
is the most recent.
    xsnap includes some asnap features and supersedes it; it also renders
XPM output [version unknown]. It is available on export or avahi.inria.fr;
see xsnap-pl2.tar.Z.
    A screen-dump and merge/edit program combining features of xwd and xpr
is available from vernam.cs.uwm.edu as xdump1.0.tar.Z. Information:
[e-mail].

    To post-process the xwd output of some of these tools, you can use xpr,
which is part of the X11 distribution. Also on several archives are xwd2ps
and XtoPS, which produce Encapsulated PostScript with trimmings suitable for
use in presentations (see export.lcs.mit.edu:contrib/xwd2ps.tar.Z and
contrib/ImageMagick.tar.Z). Also useful is the PBMPLUS package on many archive
servers; and the Xim package contains Level 2 color PostScript output.

    Also:

    Bristol Technology ([e-mail], 203-438-6969) offers Xprinter
2.0, an Xlib API for PostScript and PCL printers; a demo is on ftp.uu.net
in vendor/Bristol/Xprinter.

    ColorSoft 9619-459-8500) offers OPENprint package includes a screen-
capture facility, image-processing, and support for PostScript and
non-PostScript printers.

    Some vendors' implementations of X (e.g. DECWindows and OpenWindows)
include session managers or other desktop programs which include "print portion
of screen" or "take a snapshot" options. Some platforms also have tools which
can be used to grab the frame-buffer directly; the Sun systems, for example,
have a 'screendump' program which produces a Sun raster file. Some X terminals
have local screen-dump utilities to write PostScript to a local serial printer.

    Some vendors' implementations of lpr (e.g. Sony) include direct
support for printing xwd files, but you'll typically need some other package
to massage the output into a useful format which you can get to the printer.

----------------------------------------------------------------------
Subject:  25)! How do I make a color PostScript screendump of the X display?

    If you need color PostScript in particular, you can
    - grab the screen-image using xgrabsc to begin with, which can produce
color PostScript.
    - grab the screen-image using xwd and post-process xwd into color PS.
You can do this using xwd2ps or the XtoPS program from the ImageMagick
distribution. The PBMPLUS package is also good for this, as is the Xim package.

----------------------------------------------------------------------
Subject:  26)  How do I make a screendump including the X cursor?

    This can't be done unless the X server has been extended. Consider
instead a system-dependent mechanism for, e.g.,  capturing the frame-buffer.

----------------------------------------------------------------------
Subject:  27)! How do I convert/view Mac/TIFF/GIF/Sun/PICT/img/FAX images in X?

    The likeliest program is an incarnation of Jef Poskanzer's useful++
Portable Bitmap Toolkit, which includes a number of programs for converting
among various image formats. It includes support for many types of bitmaps,
gray-scale images, and full-color images. PBMPLUS has been updated recently;
the most recent version [12/91] is on export in contrib/pbmplus10dec91.tar.Z.
    Another tool is San Diego Supercomputing Center's IMtools ('imconv' in
particular), which packages the functionality of PBM into a single binary.
It's available anonymous ftp from sdsc.edu (132.249.20.22).

    Useful for viewing some image-formats is Jim Frost's xloadimage, a
version of which is in the R4 directory contrib/clients/xloadimage; there are
later versions available, including contrib/xloadimage.3.03.tar.Z on export.
Graeme Gill's updates to an earlier version of xloadimage are also on export;
see xli.README and xli.tar.Z.uu.

    An alternate image-viewer is xv (X Image Viewer), written by
[e-mail] (John Bradley). XV displays many image formats and
permits editing of GIF files, among others. The program was updated 5/92; see
the file contrib/xv-2.21.tar.Z on export.lcs.mit.edu.

    The Fuzzy Pixmap Manipulation, by Michael Mauldin <[e-mail]>.
Conversion and manipulation package, similar to PBMPLUS.  Version 1.0 available
via FTP as nl.cs.cmu.edu:/usr/mlm/ftp/fbm.tar.Z, uunet.uu.net:pub/fbm.tar.Z,
and ucsd.edu:graphics/fbm.tar.Z.

    The Img Software Set, by Paul Raveling <[e-mail]>, reads
and writes its own image format, displays on an X11 screen, and does some image
manipulations.  Version 1.3 is available via FTP on expo.lcs.mit.edu as
contrib/img_1.3.tar.Z, along with large collection of color images.

    The Utah RLE Toolkit is a conversion and manipulation package similar
to PBMPLUS.  Available via FTP as cs.utah.edu:pub/urt-*,
weedeater.math.yale.edu:pub/urt-*, and freebie.engin.umich.edu:pub/urt-*.

    Xim, The X Image Manipulator, by Philip Thompson, does essential
interactive displaying, editing, filtering, and converting of images. There is
a version in the X11R4 contrib area; but a more recent version (using R4 and
Motif 1.1) is available from gis.mit.edu (18.80.1.118). Xim reads/writes gif,
xwd, xbm, tiff, rle, xim, (writes level 2 eps) and other formats and also has a
library and command-line utilities for building your own applications.

    ImageMagick [2.1b] by [e-mail] can be retrieved from export's
contrib area. It is a collection of utilities to transform and display images
on any X server. The tool uses the MIFF format; filters to and from MIFF from
other popular formats (PPM, TIFF, GIF, SUN Raster, etc) are included.

    xtiff is a tool for viewing a TIFF file in an X window.  It was written
to handle as many different kinds of TIFF files as possible while remaining
simple, portable and efficient.  xtiff illustrates some common problems
with building pixmaps and using different visual classes.  It is distributed
as part of Sam Leffler's libtiff package and it is also available on
export.lcs.mit.edu, uunet.uu.net and comp.sources.x. [[e-mail],10/90]
xtiff 2.0 was announced in 4/91; it includes Xlib and Xt versions.

    A version of Lee Iverson's ([e-mail]) image-viewing tool
is available as contrib/vimage-0.9.3.tar.Z on export.lcs.mit.edu.  The package
also includes an ImageViewPort widget and a FileDialog widget. [12/91;5/92]

[some material from Larry Carroll ([e-mail]), 5/91]

----------------------------------------------------------------------
Subject:  28)  How can I change the titlebar of my xterm window?

    The solution involves sending an escape sequence to xterm which will
cause it to update the property which the window manager relies upon for the
string which appears in the window titlebar.
    A solution is as easy as typing this in an xterm running a shell:
        echo "ESC]2;TEXT^G"
where ESC is the escape key, TEXT is the string you wish to have displayed,
and ^G is a Control-G (the BEL character).

    Here is a more complicated csh alias which changes the titlebar to
the current working directory when you change directories:
        alias newcd 'cd \!*; echo -n ESC]2\;$cwd^G'

    The digit '2' in these strings indicates to xterm that it should
change only the title of the window; to change both the title and the name
used in the icon, use the digit '0' instead, and use '1' to change only the
icon name.

    Note: another way to do this, which prevents an incorrect display of
the local directory if a modified `cd` is used in a subshell, is to wrap the
escape sequences into the PS1 prompt itself.

    Note: on an IBM RS/6000 is may be necessary to begin the sequence with
a ^V.

----------------------------------------------------------------------
Subject:  29)  Where can I find the xterm control sequences?

The best source of such information is in your R5 sources in the file
ctlseqs.ms; a PostScript version is in mit/hardcopy/clients/ctlseqs.PS.Z.

Other good sources of information include the R4 version of that document
and also the file in the R4 sources called mit/clients/xterm/ctlseq2.txt, a
compilation put together by Skip Montanaro (GE CR&D) listing the VT100
sequences. It dates from R3 but is fairly accurate.  A hardcopy version was
published in the December 1989 XNextEvent (the XUG newsletter).

In addition, Volume 3 (User's Guide) of the R4 flavor of the O'Reilly
X Window System series contains an appendix listing xterm control sequences;
it is less accurate than the information in the R5 or R4 sources.

In a pinch, a VT100 manual will do.

[last updated 10/91]

----------------------------------------------------------------------
Subject:  30)  Why does the R3 xterm, et al, fail against the R4 server?

    The value given to a window's do_not_propagate mask is the likely
culprit.  R3 allowed bogus values to be set, and early version of both Andrew
and InterViews did, as well. Similar problems also occur in the R3 Motif
PanedWindow widget.
    If it is impossible to fix client source -- and many systems still ship
the R3 xterm -- use 'xset bc' to put the X11R4 server into bug-compatibility
mode.

----------------------------------------------------------------------
Subject:  31)  How can I use characters above ASCII 127 in xterm ?

    In order to use special characters such as the o-umlaut, you need to
"stty pass8" but also to use a charcell ISO8859 font, such as
    XTerm*font:     -*-*-medium-r-normal-*-*-130-*-*-c-*-iso8859-1
    XTerm*boldfont:    -*-*-bold-r-normal-*-*-130-*-*-c-*-iso8859-1
[The family is intentionally unspecified in this example.]

In addition, you may want to set this in your shell:
    setenv LC_CTYPE iso_8859_1

        For a given character above 127, you can determine the key to use with
the Alt modifier by finding the equivalent character below 127 (try using
`man ascii`). For example, o-umlaut (v) is Alt-v and the section character (')
is Alt-'.

[thanks to Greg Holmberg ([e-mail]) and Stephen Gildea
([e-mail]); 6/92]

----------------------------------------------------------------------
Subject:  32)  Why are my xterm menus so small?

    You are probably setting the geometry small accidentally. If you give
a resource specification like this:
        xterm*geometry: 80x24
then you are asking for all widgets under xterm to have their geometry set to
80x24. For the main window, this is OK, as it uses characters for its size.
But its popup menus don't; they are in pixels and show up small. To set only
the terminal widget to have the specified geometry, name it explicitly:
        xterm*VT100.geometry: 80x24

----------------------------------------------------------------------
Subject:  33)  How can I print the current selection?

    You could paste it into an xterm after executing the lpr command.
However, a program by Richard Hesketh ([e-mail]) specifically for
manipulating the selection will help; e.g.
    % xselection PRIMARY | lpr
finds the primary selection and prints it. This command can be placed in a
window-manager menu or in shell-scripts. xselection also permits the setting of
the selection and other properties. A version is on export.
    Also available is ria.ccs.uwo.ca:pub/xget_selection.tar.Z, which can be
adapted to do this.

----------------------------------------------------------------------
Subject:  34)  How does Xt use environment variables in loading resources?

    You can use several environment variables to control how resources are
loaded for your Xt-based programs -- XFILESEARCHPATH, XUSERFILESEARCHPATH, and
XAPPLRESDIR.  These environment variables control where Xt looks for
application-defaults files as an application is initializing.  Xt loads at most
one app-defaults file from the path defined in XFILESEARCHPATH and another from
the path defined in XUSERFILESEARCHPATH.

    Set XFILESEARCHPATH if software is installed on your system in such a
way that app-defaults files appear in several different directory hierarchies.
Suppose, for example, that you are running Sun's Open Windows, and you also
have some R4 X applications installed in /usr/lib/X11/app-defaults. You could
set a value like this for XFILESEARCHPATH, and it would cause Xt to look up
app-defaults files in both /usr/lib/X11 and /usr/openwin/lib (or wherever your
OPENWINHOME is located):
    setenv XFILESEARCHPATH /usr/lib/X11/%T/%N:$OPENWINHOME/lib/%T/%N

    The value of this environment variable is a colon-separated list of
pathnames.  The pathnames contain replacement characters as follows:
    %T        the literal string "app-defaults" [works only in
            XFILESEARCHPATH]
    %N        application class name
    %C        customization resource (R5 only)
    %L        language, locale, and codeset (e.g. "ja_JP.EUC")
    %l        language part of %L  (e.g. "ja")

    Let's take apart the example.  Suppose the application's class name is
"Myterm". Also, suppose Open Windows is installed in /usr/openwin. (Notice the
example omits locale-specific lookup.)
    /usr/lib/X11/%T/%N        means /usr/lib/X11/app-defaults/Myterm
    $OPENWINHOME/lib/%T/%N    means /usr/openwin/lib/app-defaults/Myterm

    As the application initializes, Xt tries to open both of the above
app-defaults files, in the order shown.  As soon as it finds one, it reads it
and uses it, and stops looking for others.  The effect of this path is to
search first in /usr/lib/X11, then in /usr/openwin.

    Let's consider another example. This time, let's set
XUSERFILESEARCHPATH so it looks for the file Myterm.ad in the current working
directory, then for Myterm in the directory ~/app-defaults.
    setenv XUSERFILESEARCHPATH ./%N.ad:$HOME/app-defaults/%N

    The first path in the list expands to ./Myterm.ad.  The second expands
to $HOME/app-defaults/Myterm.  This is a convenient setting for debugging
because it follows the Imake convention of naming the app-defaults file
Myterm.ad in the application's source directory, so you can run the application
from the directory in which you are working and still have the resources loaded
properly.

    With R5, there's another twist.  You may specify a customization
resource value.  For example, you might run the "myterm" application like this:
    myterm -xrm "*customization: -color"

    If one of your pathname specifications had the value
"/usr/lib/X11/%T/%N%C" then the expanded pathname would be
"/usr/lib/X11/app-defaults/Myterm-color" because the %C substitution character
takes on the value of the customization resource.

    The default XFILESEARCHPATH, compiled into Xt, is:
        /usr/lib/X11/%L/%T/%N%C:\  (R5)
        /usr/lib/X11/%l/%T/%N%C:\  (R5)
        /usr/lib/X11/%T/%N%C:\     (R5)
        /usr/lib/X11/%L/%T/%N:\
        /usr/lib/X11/%l/%T/%N:\
        /usr/lib/X11/%T/%N

    (Note: some sites replace /usr/lib/X11 with a ProjectRoot in
this batch of default settings.)

    The default XUSERFILESEARCHPATH, also compiled into Xt, is
        <root>/%L/%N%C:\  (R5)
        <root>/%l/%N%C:\  (R5)
        <root>/%N%C:\     (R5)
        <root>/%L/%N:\
        <root>/%l/%N:\
        <root>/%N:

    <root> is either the value of XAPPLRESDIR or the user's home directory
if XAPPLRESDIR is not set.  If you set XUSERFILESEARCHPATH to some value other
than the default, Xt ignores XAPPLRESDIR altogether.

    Notice that the quick and dirty way of making your application find
your app-defaults file in your current working directory is to set XAPPLRESDIR
to ".", a single dot.  In R3, all this machinery worked differently; for R3
compatibilty, many people set their XAPPLRESDIR value to "./", a dot followed
by a slash.

[Thanks to Oliver Jones ([e-mail]) and Peter Ware, 8/92]

----------------------------------------------------------------------

David B. Lewis                     [e-mail]

        "Just the FAQs, ma'am." -- Joe Friday
--
David B. Lewis        Temporarily at but not speaking for Visual, Inc.
day: [e-mail]    evening: [e-mail]